Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding windows-hpc-base-image #3663

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

marosset
Copy link

@marosset marosset commented Jul 1, 2024

What type of PR is this?

/kind feature

What this PR does / why we need it:

kubernetes/kubernetes#125297 is adding a Windows flavor to the kube-proxy image and there was some concern about basing the image on another image hosted at mcr.microsoft.com.

This PR adds a windows container base image that other images (like the Windows kube-proxy image) can be based on and is functionally equivalent to the image mcr.microsoft.com/oss/kubernetes/windows-host-process-containers-base-image:v1.0.0 but can be built and hosted in K8s community resouces

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

None

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/feature Categorizes issue or PR as related to a new feature. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jul 1, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: marosset
Once this PR has been reviewed and has the lgtm label, please assign xmudrii for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jul 1, 2024
@marosset
Copy link
Author

marosset commented Jul 1, 2024

/cc @claudiubelu @BenTheElder @xmudrii

@@ -0,0 +1,121 @@
Creative Commons Legal Code
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we just use the repo's ASLv2?

the resulting image on top of the base will be largely ASLv2 anyhow.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The equivalent image that gets published to MCR was released with the CC0 license - https://github.com/microsoft/windows-host-process-containers-base-image/blob/main/cc0-license.txt

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean we're going to build ASLv2 images with this, and CC0 is NOT on the CNCF approved list so we should not be using any CC0 images.

Are we using CC0 anywhere else ...?

https://github.com/cncf/foundation/blob/main/allowed-third-party-license-policy.md

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct.

Copy link
Member

@puerco puerco Jul 3, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also (I'm sure you saw mark) the script and Makefile need the boilerplate repo headers, and the automation will look for the apache license and fail if we use a different one.

Copy link
Member

@puerco puerco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I started reviewing this yesterday. I have a few comments, one of them is about the license which Ben already mentioned

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the reason behind releasing this under CC0? I have no particular feelings or thoughts but LF legal may have opinions here. (I've had to switch licenses for other projects based on their input).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we rename this to cloudbuild.yaml to match other files in the repo?

Comment on lines 14 to 15
touch "$BUILD_DIR/layer/Files/Windows/System32/config/DEFAULT"
echo "" > "$BUILD_DIR/layer/Files/Windows/System32/config/DEFAULT"
Copy link
Member

@puerco puerco Jul 2, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the touch lines here are superfluous. Maybe drop them?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I can remove the echo actually.
Let me verify and I'll remove one or the other

To publish the image to a registry:

```sh
REGISTRY=gcr.io/k8s-staging-releng VERSION=v0.1.0 make image_publish
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The image image_publish target is missing from the makefile above.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that should be image_push :-/ - i'll update

@k8s-ci-robot
Copy link
Contributor

@marosset: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-release-verify 935ee79 link true /test pull-release-verify

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. needs-priority release-note-none Denotes a PR that doesn't merit a release note. sig/release Categorizes an issue or PR as relevant to SIG Release. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants